Re: backup manifests and contemporaneous buildfarm failures
Fabien COELHO <coelho@cri.ensmp.fr>
Commits
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Try to avoid compiler warnings in optimized builds.
- 05021a2c0cd2 13.0 landed
-
Fix option related issues in pg_verifybackup.
- 0a89e93bfaa6 13.0 landed
-
Add index term for backup manifest in documentation.
- 4db819ba4039 13.0 landed
-
Code review for backup manifest.
- a2ac73e7be7a 13.0 landed
-
Document the backup manifest file format.
- 149f2ae88ab0 13.0 landed
-
Fix typo in pg_validatebackup documentation.
- c4f82a779d26 13.0 landed
-
Exclude backup_manifest file that existed in database, from BASE_BACKUP.
- 1ec50a81ec0a 13.0 landed
-
Msys2 tweaks for pg_validatebackup corruption test
- c3e4cbaab936 13.0 landed
-
Fix resource management bug with replication=database.
- 3e0d80fd8d3d 13.0 cited
-
Be more careful about time_t vs. pg_time_t in basebackup.c.
- db1531cae009 13.0 cited
-
pg_validatebackup: Fix 'make clean' to remove tmp_check.
- 9f8f881caa0f 13.0 landed
-
pg_validatebackup: Also use perl2host in TAP tests.
- 460314db08e8 13.0 landed
-
Generate backup manifests for base backups, and validate them.
- 0d8c9c1210c4 13.0 landed
-
Add checksum helper functions.
- c12e43a2e0d4 13.0 landed
-
pg_waldump: Add a --quiet option.
- ac44367efbef 13.0 landed
-
Catversion bump for b9b408c48724
- afb5465e0cfc 13.0 cited
-
pg_basebackup: Refactor code for reading COPY and tar data.
- 431ba7bebf13 13.0 landed
-
Use a ResourceOwner to track buffer pins in all cases.
- 3cb646264e8c 12.0 cited
-
Use ARMv8 CRC instructions where available.
- f044d71e331d 11.0 cited
-
Logical replication support for initial data copy
- 7c4f52409a8c 10.0 cited
-
Use Intel SSE 4.2 CRC instructions where available.
- 3dc2d62d0486 9.5.0 cited
-
Switch to CRC-32C in WAL and other places.
- 5028f22f6eb0 9.5.0 cited
-
Remove support for 64-bit CRC.
- 404bc51cde9d 9.5.0 cited
-
Change CRCs in WAL records from 64bit to 32bit for performance reasons.
- 21fda22ec46d 8.1.0 cited
Hello Robert, > Done now. Meanwhile, two more machines have reported the mysterious message: > > sh: ./configure: not found > > ...that first appeared on spurfowl a few hours ago. The other two > machines are eelpout and elver, both of which list Thomas Munro as a > maintainer. spurfowl lists Stephen Frost. Thomas, Stephen, can one of > you check and see what's going on? spurfowl has failed this way four > times now, and eelpout and elver have each failed the last two runs, > but since there's no helpful information in the logs, it's hard to > guess what went wrong. > > I'm sort of afraid that something in the new TAP tests accidentally > removed way too many files during the cleanup phase - e.g. it decided > the temporary directory was / and removed every file it could access, > or something like that. It doesn't do that here, or I, uh, would've > noticed by now. But sometimes strange things happen on other people's > machines. Hopefully one of those strange things is not that my test > code is single-handedly destroying the entire buildfarm, but it's > possible. seawasp just failed the same way. Good news, I can see "configure" under "HEAD/pgsql". The only strange thing under buildroot I found is: HEAD/pgsql.build/src/bin/pg_validatebackup/tmp_check/t_003_corruption_master_data/backup/open_directory_fails/pg_subtrans/ this last directory perms are d--------- which seems to break cleanup. It may be a left over from a previous run which failed (possibly 21dc488 ?). I cannot see how this would be related to configure, though. Maybe something else fails silently and the message is about a consequence of the prior silent failure. I commented out the cron job and will try to look into it on tomorrow if the status has not changed by then. -- Fabien.