Problems with the CI infrastructure?
Hi, I must admit I don't know much about the CI/autopkgtest infrastructure, but I've noticed over summer that the frequency at which my packages are being tested has decreased a lot, especially when it comes to ordinary tests in unstable (as opposed to tests that pick a few packages from experimental). Has there been some change to the CI infrastructure? Is it experiencing problems? Am I just missing something? Best, Gard signature.asc Description: PGP signature
Re: Problems with the CI infrastructure?
On Fri, Sep 18, 2020 at 09:43:32AM +0200, Gard Spreemann wrote: > Hi, > > I must admit I don't know much about the CI/autopkgtest infrastructure, > but I've noticed over summer that the frequency at which my packages are > being tested has decreased a lot, especially when it comes to ordinary > tests in unstable (as opposed to tests that pick a few packages from > experimental). > > Has there been some change to the CI infrastructure? Is it experiencing > problems? Am I just missing something? At the moment we are not running the "unstable only" tests automatically. There is work that needs to be done to improve the efficiency of the unstable only scheduling, to avoid overwhelming the system. You can still trigger them using the self-service interface though. For now the only tests that are being triggered automatically are for unstable->testing migration, and the experimental->unstable tests. The process that does that will also trigger pure unstable tests, but not as often as we had before. signature.asc Description: PGP signature
Re: [External] Re: Lenovo discount portal update (and a few other things)
On 9/17/2020 5:12 AM, Yves-Alexis Perez wrote: On Wed, 2020-09-02 at 15:30 -0400, Mark Pearson wrote: On 9/2/2020 2:19 PM, Yves-Alexis Perez wrote: We're still working on getting other geographies up and running - not available yet I'm afraid. Any idea of the timeframe? Weeks, months, more? Afraid I don't know but I hope it's not months...it will depend on the geo teams to some extent. The US site took us a few weeks to get up but that was the first oneso fingers crossed the others are easier. My colleague is chasing the others down so I'll check with him what the status is. Hi Mark, did you have an update from your colleague on the other geos? Regards, - -- Yves-Alexis Sorry - no update yet. I'll keep pushing Mark
Bug#970559: ITP: glab -- An open-source GitLab command line tool
Package: wnpp Severity: wishlist Owner: TODO * Package name: glab Version : 1.10.0-1 Upstream Author : Clement Sam * URL : https://github.com/profclems/glab * License : Expat Programming Lang: Go Description : An open-source GitLab command line tool GLab . All Contributors (#contributors-) . . Go Report Card (https://goreportcard.com/report/github.com/profclems/glab) GitHub Workflow Status .github/workflows/build_docs.yml Gitter (https://gitter.im/glabcli/community?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge) License (LICENSE) Twitter (https://twitter.com/intent/tweet?text=Take%20Gitlab%20to%20the%20command%20line%20with%20%23glab,%20an%20open-source%20GitLab%20CLI%20tool:&url=https%3A%2F%2Fgithub.com%2Fprofclems%2Fglab) . GLab is an open source Gitlab Cli tool written in Go (golang) to help work seamlessly with Gitlab from the command line. Work with issues, merge requests, watch running pipelines directly from your CLI among other features. . image Usage bash glab [flags] . Core Commands• glab mr [list, create, close, reopen, delete]• glab issue [list, create, close, reopen, delete]• glab pipeline [list, delete, ci status, ci view]• glab config• glab helpExamples bash $ glab issue create --title="This is an issue title" --description="This is a really long description" $ glab issue list --closed $ glab pipeline ci view -b master# to watch the latest pipeline on master $ glab pipeline status# classic ci view . Learn More Read the documentation (https://clementsam.tech/glab) for more information on this tool. Support glab 💖 By donating $5 or more you can support the ongoing development of this project. We'll appreciate some support. Thank you to all our supporters! 🙏 [Contribute (https://opencollective.com/glab/contribute)] Individuals This project exists thanks to all the people who contribute. [Contribute (https://github.com/profclems/glab/blob/trunk/.github/CONTRIBUTING.md)]. . Backers Thank you to all our backers! 🙏 [Become a backer (https://opencollective.com/glab/contribute)] . Installation Download a binary suitable for your OS at the releases page (https://github.com/profclems/glab/releases/latest). Quick Install (Bash) You can install or update glab with: bash curl -sL https://j.mp/glab-i | sudo bash . or bash curl -s https://raw.githubusercontent.com/profclems/glab/trunk/scripts/quick_install.sh | sudo bash . Installs into usr/local/bin . NOTE: Please take care when running scripts in this fashion. Consider peaking at the install script itself and verify that it works as intended. Windows Available for download on scoop or manually as an installable executable file or a Portable archived file in tar and zip formats at the releases page (https://github.com/profclems/glab/releases/latest). Download and install now at the releases page (https://github.com/profclems/glab/releases/latest). . The installable executable file sets the PATH automatically. Scoop sh scoop bucket add profclems-bucket https://github.com/profclems/scoop-bucket.git scoop install glab . Linux Downloads available via linuxbrew (homebrew) and tar balls Linuxbrew (Homebrew) sh brew install profclems/tap/glab . Updating: sh brew upgrade glab . Arch Linux glab is available through the gitlab-glab-bin (https://aur.archlinux.org/packages/gitlab-glab-bin/) package on the AUR. Manual Installation Download the tar ball, untar and install: • Download the .tar.gz file from the releases page (https://github.com/profclems/glab/releases/latest)• unzip glab-*-linux-amd64.tar.gz to unzip the downloaded file• sudo mv glab-*-linux-amd64/glab /usr/binMacOS glab is available via Homebrew or you can manually install Homebrew sh brew install profclems/tap/glab . Updating: sh brew upgrade glab . Installing manually• Download the .tar.gz or .zip file from the releases page (https://github.com/profclems/glab/releases/latest) and unzip or untar• ls /usr/local/bin/ || sudo mkdir /usr/local/bin/; to make sure the bin folder exists• sudo mv glab-*-darwin-amd64/glab /usr/binBuilding From Source If a supported binary for your OS is not found at the releases page (https://github.com/profclems/glab/releases/latest), you can build from source: • Verify that you have Go 1.13.8+ installed sh $ go version go version go1.14 . . If go is not installed, follow instructions on the Go website (https://golang.org/doc/install). • Clone this repository sh $ git clone https://github.com/profclems/glab.git glab-cli $ cd glab-cli . . or . sh $ git clone https://gitlab.com/profclems/glab.git $ cd glab-cli . • Build the project . $ make build . • Move the resulting bin/glab executable to somewhere in your PATH sh $ sudo mv ./bin/glab /usr/local/bin/ . or sh $ sudo mv ./bin/glab /usr/bin/ . • Run glab version to check if it worked and glab config -g to set upConfigura
Bug#970560: ITP: glab -- An open-source GitLab command line tool
Package: wnpp Severity: wishlist Owner: TODO * Package name: glab Version : 1.10.0-1 Upstream Author : Clement Sam * URL : https://github.com/profclems/glab * License : Expat Programming Lang: Go Description : An open-source GitLab command line tool GLab . All Contributors (#contributors-) . . Go Report Card (https://goreportcard.com/report/github.com/profclems/glab) GitHub Workflow Status .github/workflows/build_docs.yml Gitter (https://gitter.im/glabcli/community?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge) License (LICENSE) Twitter (https://twitter.com/intent/tweet?text=Take%20Gitlab%20to%20the%20command%20line%20with%20%23glab,%20an%20open-source%20GitLab%20CLI%20tool:&url=https%3A%2F%2Fgithub.com%2Fprofclems%2Fglab) . GLab is an open source Gitlab Cli tool written in Go (golang) to help work seamlessly with Gitlab from the command line. Work with issues, merge requests, watch running pipelines directly from your CLI among other features. . image Usage bash glab [flags] . Core Commands• glab mr [list, create, close, reopen, delete]• glab issue [list, create, close, reopen, delete]• glab pipeline [list, delete, ci status, ci view]• glab config• glab helpExamples bash $ glab issue create --title="This is an issue title" --description="This is a really long description" $ glab issue list --closed $ glab pipeline ci view -b master# to watch the latest pipeline on master $ glab pipeline status# classic ci view . Learn More Read the documentation (https://clementsam.tech/glab) for more information on this tool. Support glab 💖 By donating $5 or more you can support the ongoing development of this project. We'll appreciate some support. Thank you to all our supporters! 🙏 [Contribute (https://opencollective.com/glab/contribute)] Individuals This project exists thanks to all the people who contribute. [Contribute (https://github.com/profclems/glab/blob/trunk/.github/CONTRIBUTING.md)]. . Backers Thank you to all our backers! 🙏 [Become a backer (https://opencollective.com/glab/contribute)] . Installation Download a binary suitable for your OS at the releases page (https://github.com/profclems/glab/releases/latest). Quick Install (Bash) You can install or update glab with: bash curl -sL https://j.mp/glab-i | sudo bash . or bash curl -s https://raw.githubusercontent.com/profclems/glab/trunk/scripts/quick_install.sh | sudo bash . Installs into usr/local/bin . NOTE: Please take care when running scripts in this fashion. Consider peaking at the install script itself and verify that it works as intended. Windows Available for download on scoop or manually as an installable executable file or a Portable archived file in tar and zip formats at the releases page (https://github.com/profclems/glab/releases/latest). Download and install now at the releases page (https://github.com/profclems/glab/releases/latest). . The installable executable file sets the PATH automatically. Scoop sh scoop bucket add profclems-bucket https://github.com/profclems/scoop-bucket.git scoop install glab . Linux Downloads available via linuxbrew (homebrew) and tar balls Linuxbrew (Homebrew) sh brew install profclems/tap/glab . Updating: sh brew upgrade glab . Arch Linux glab is available through the gitlab-glab-bin (https://aur.archlinux.org/packages/gitlab-glab-bin/) package on the AUR. Manual Installation Download the tar ball, untar and install: • Download the .tar.gz file from the releases page (https://github.com/profclems/glab/releases/latest)• unzip glab-*-linux-amd64.tar.gz to unzip the downloaded file• sudo mv glab-*-linux-amd64/glab /usr/binMacOS glab is available via Homebrew or you can manually install Homebrew sh brew install profclems/tap/glab . Updating: sh brew upgrade glab . Installing manually• Download the .tar.gz or .zip file from the releases page (https://github.com/profclems/glab/releases/latest) and unzip or untar• ls /usr/local/bin/ || sudo mkdir /usr/local/bin/; to make sure the bin folder exists• sudo mv glab-*-darwin-amd64/glab /usr/binBuilding From Source If a supported binary for your OS is not found at the releases page (https://github.com/profclems/glab/releases/latest), you can build from source: • Verify that you have Go 1.13.8+ installed sh $ go version go version go1.14 . . If go is not installed, follow instructions on the Go website (https://golang.org/doc/install). • Clone this repository sh $ git clone https://github.com/profclems/glab.git glab-cli $ cd glab-cli . . or . sh $ git clone https://gitlab.com/profclems/glab.git $ cd glab-cli . • Build the project . $ make build . • Move the resulting bin/glab executable to somewhere in your PATH sh $ sudo mv ./bin/glab /usr/local/bin/ . or sh $ sudo mv ./bin/glab /usr/bin/ . • Run glab version to check if it worked and glab config -g to set upConfigura
Mass bugs filing: autopkgtest should be marked superficial (new list)
Hi All, If the test done in the autopkgtest does not provide significant test coverage then it should be marked with "Restrictions: superficial". Ref: https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/doc/README.package-tests.rst Examples of tests which are not significant includes (its not a complete list): 1) Executing the binary to check version Test-Command: foo -v Test-Command: foo -V Test-Command: foo --version 2) Executing the binary to check help (foo -h) Test-Command: foo -h Test-Command: foo --help 3) checking for files installed with 'ls'. Test-Command: ls -l /usr/lib/*/foo.so 4) A Python or Perl library runs import foo or require Foo; but does not attempt to use the library beyond that. Test-Command: python3 -c "import foo" I intend to file them with "severity: serious" as packages with non-trivial autopkgtests enjoy a reduced age for migration from unstable to testing and they are also allowed to migrate in a later stage of the freeze than other packages. Ref: https://release.debian.org/bullseye/freeze_policy.html And, rc_policy confirms "These tests must test at least one of its own installed binary packages in some way, or must be marked as superficial". Ref: https://release.debian.org/bullseye/rc_policy.txt Also, Paul has confirmed that if its fixed in git but not uploaded then the severity can be reduced while marking the bug as pending. Ref: https://lists.debian.org/debian-devel/2020/09/msg00236.html Attached is the dd-list. -- Regards Sudip dd-list Description: Binary data
Re: Mass bugs filing: autopkgtest should be marked superficial (new list)
On Fri, Sep 18, 2020 at 09:21:52PM +0100, Sudip Mukherjee wrote: > If the test done in the autopkgtest does not provide significant test > coverage then it should be marked with "Restrictions: superficial". > Ref: > https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/doc/README.package-tests.rst [...] > I intend to file them with "severity: serious" [...] sigh. I too would appreciate if these bugs were filed with severity:important in the first place, not the least to avoid discussions like these. seriously, these packages are only cosmetically seriously buggy and important (and normal) bugs should be fixed as well, anyhow. so why inflate the severity and discussions if the same can be achieved cheaper and much nicer by just using lower severity? please use important and announce to bump the severity (to serious) in 1-3 months from now, as these bugs really must not make it into bullseye! but give people some slack to support your cause. an important bug and being listed on d-devel is serious enough. the world is on fire and these are just superficial tests. -- cheers, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C signature.asc Description: PGP signature
Re: Mass bugs filing: autopkgtest should be marked superficial (new list)
On Fri, Sep 18, 2020 at 09:21:52PM +0100, Sudip Mukherjee wrote: [...] sigh. I forgot to thank you for all the work you put into this! I *very* much appreciate good tests and your work to improve the quality of autopkgtests! I'm sorry this severity detail distracted me from expressing this. So: whatever severity you choose, thank you for all these bugs! :) -- cheers, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C signature.asc Description: PGP signature
Bug#970575: ITP: pytorch-geometric -- Geometric Deep Learning Extension Library for PyTorch
Package: wnpp Severity: wishlist Owner: Mo Zhou X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: pytorch-geometric * URL : https://github.com/rusty1s/pytorch_geometric * License : MIT/X Programming Lang: Python Description : Geometric Deep Learning Extension Library for PyTorch Debian Deep Learning Team
