Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DO NOT MERGE: expansion of dwalsh's comparison script #1

Closed
wants to merge 2 commits into from

Conversation

edsantiago
Copy link

Something that compares all subcommands. It's a horrible
mess because some man pages display COMMANDS and some
display SUBCOMMANDS; and some show the subcommand name
in the first column, others show the podman-xxx man page;
and there are inconsistencies galore.

This is a fake PR so Dan can look at the rest of the
inconsistencies that his script didn't look at

Signed-off-by: Ed Santiago santiago@redhat.com

rhatdan and others added 2 commits February 27, 2019 12:52
Also add podman-commands.sh to compare man pages to commands.

Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
Something that compares _all_ subcommands. It's a horrible
mess because some man pages display COMMANDS and some
display SUBCOMMANDS; and some show the subcommand name
in the first column, others show the podman-xxx man page;
and there are inconsistencies galore.

This is a fake PR so Dan can look at the rest of the
inconsistencies that his script didn't look at

Signed-off-by: Ed Santiago <santiago@redhat.com>
@edsantiago
Copy link
Author

@rhatdan what a can of worms! I hope this helps you expand upon your PR

@rhatdan rhatdan force-pushed the man branch 7 times, most recently from 876505c to b4b7b29 Compare February 27, 2019 21:37
@rhatdan
Copy link
Owner

rhatdan commented Feb 28, 2019

@edsantiago Nice, I moved my script to hack/ directory, Could you fix this PR to point to there.

Does your script check all of the subcommands?

podman
podman-volume
podman-container
podman-pod
podman-image
podman-play
podman-generate

@edsantiago
Copy link
Author

@rhatdan my logic is to run podman XXX --help for all XXX found in podman help. If the usage message is of the form podman XXX [command] -- a convention followed by all the subcommands you list, and by no non-subcommands -- then it recurses into XXX as a subcommand. The idea being, if next month someone adds a podman jiggledybonk subcommand, this script would automatically find it and compare subcommands.

I will clean up my code and resubmit it under hack, thanks.

@edsantiago edsantiago closed this Feb 28, 2019
@edsantiago edsantiago deleted the pr2470_esm branch February 28, 2019 18:18
rhatdan pushed a commit that referenced this pull request Jul 11, 2019
It's desirable to make archives available of builds containing actual
tested content.  While not official distro-releases, these will enable
third-party testing, experimentation, and development for both branches
(e.g. "master") and pull requests (e.g. "pr3106").

* Add a Makefile targets for archiving both regular podman binaries
  and the remote-client.  Encode release metadata within these
  archives so that their exact source can be identified.

* Fix bug with cross-compiling remote clients for the Windows and Darwin
  platforms.

* Add unit-testing of cross-compiles for Windows and Darwin platforms.

* A few small CI-script typo-fixes

* Add a script which operates in two modes:

  1. Call Makefile targets which produce release archives.
     Upload the archive to Cirrus-CI's built-in caching system
     using reproducible cache keys.

  2. Utilize reproduced cache keys to attempt download of cache
     from each tasks.  When successful, parse the file's
     release metadata, using it to name the archive file.  Upload
     all recovered archives to a publicly accessible storage bucket
     for future reference.

* Update the main testing task to call the script in mode #1 for
  all primary platforms.

* Add a new `$SPECIALMODE` task to call the script in mode #1 for
  Windows and Darwin targets.

* Add a new 'release' task to the CI system, dependent upon all other
  tasks.  This new tasks executes the script in mode #2.

* Update CI documentation

Signed-off-by: Chris Evich <cevich@redhat.com>
rhatdan pushed a commit that referenced this pull request Jun 15, 2020
rhatdan pushed a commit that referenced this pull request Apr 28, 2021
Our current #1 flake; this is a simple one: we can't run 'logs'
on a container run with '-d --rm'.

Signed-off-by: Ed Santiago <santiago@redhat.com>
rhatdan pushed a commit that referenced this pull request Sep 8, 2021
go test -v -p 1 -tags apparmor,ostree,seccomp,selinux,systemd github.com/containers/podman/v2/test/testvol
results in the following error:

> test/testvol/main.go:227:10: Errorf format %s reads arg #1, but call has 0 args
> test/testvol/main.go:233:10: Errorf format %s reads arg #1, but call has 0 args

This patch passes req.Name as an argument to the Errorf() call

Signed-off-by: Raoul Bhatia <raoul.bhatia@radarcs.com>
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 29, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants