It would appear https://registry.hub.docker.com/r/buildkite/plugin-tester/tags that no version of this image is built for the arm64 platform.

Is that an oversight or is there a workaround that I'm missing, for running this image on M1s?

I would like to run bats outside of Docker, which I find to be finicky and can never remember the start commands, but it's not clear where to find load.bash.

Error Message: Error: BATS_TMPDIR (/tmp) is not writable🚨 Error: The command exited with status 1

Docker-in-Docker (dind) problem, when trying to use the buildkite-plugins/docker-buildkite-plugin with the docker image generated by this repository (buildkite-plugins/buildkite-plugin-tester) for buildkite/plugin-tester

Related to new sys call (faccessat2) introduced in Linux Kernel v5.8 returning error code EPERM instead of ENOSYS, affects glibc, runc, seccomp/libseccomp, moby...etc.

PR Raised to fix problem: #55

BATS 1.2.0 came out in April - would you mind pushing an updated image please? https://github.com/bats-core/bats-core/releases/tag/v1.2.0

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

File: renovate.json
Error type: The renovate configuration file contains some invalid settings
Message: Invalid configuration option: docker-compose.pinDependencies

Issue

the stub command from the bats-mock library is normally able to take the * to denote that the stub will handle any arguments for the given command/binary that's being stubbed. This functionality is no longer usable, as the * now globs files present in the working directory.

Example invocation:

stub buildkite-agent "* : exit 0"

Example output:

 bats-mock(buildkite-agent): got buildkite-agent annotate --style error failed to run uname<br /> --context trivy-scan                                                                                                                                                                                                  16/30
bats-mock(buildkite-agent): patterns  [7] = 'LICENSE' 'Makefile' 'README.md' 'hooks' 'plugin.yml' 'renovate.json' 'tests'
bats-mock(buildkite-agent): arguments [6] = 'annotate' '--style' 'error' 'failed\ to\ run\ uname\<br\ /\>' '--context' 'trivy-scan'
bats-mock(buildkite-agent): match failed at idx 0, expected 'LICENSE', got 'annotate'
bats-mock(buildkite-agent): result 1
bats-mock(buildkite-agent): unstubbing

Expected behavior

Using the following format should stub the command with any given number of parameters:

stub <command> "* : <stub command>"

Broken since

buildkite plugin-tester v3.0.0

Note that it's still broken in v3.0.1

Worked in

buildkite plugin-tester v2.0.0

Check and fix the build status on the master repo which is stuck on red for a long time

Test zap

We used to have this:

# https://github.com/buildkite-plugins/buildkite-plugin-tester
load "$BATS_PATH/load.bash"

However, at least one of our agents downloaded a new version of the buildkite/plugin-tester image, which no longer loads load.bash:

bats: /load.bash does not exist

So I read through the README and found that this has been changed to BATS_PLUGIN_PATH, and now I am getting the opposite issue, on another agent that cached an older version of plugin-tester.

bats: /load.bash does not exist

Updating our plugin's tests has been a super finicky process. It would be nice if things that aren't usually expected to break - images - didn't cause more unexpected failures.

I had to fix my version to v3.0.1 as v.4.0.1 didn't allows me to stub anymore the buildkite-agent

Unfortunately, when looking at v3.0.1...v4.0.0 I can see the new source https://github.com/buildkite-plugins/bats-mock/archive/v2.1.0.tar.gz but it is not visible publicly. So I have no idea of the change required. The doc is also referencing the original repo too.

I don't expect any breaking changes with stub therefore.

Sample Bat tests

https://github.com/iress/junit-slack-notification-buildkite-plugin/blob/main/tests/command.bats

Output running v4.0.0

affected code

stub buildkite-agent 'artifact download : echo Download artifacts'

unstub buildkite-agent

Workaround:

fixed version - https://github.com/iress/junit-slack-notification-buildkite-plugin/pull/9/files

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

This repository currently has no open or pending branches.

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Hey! We're hitting the issues that were fixed in #17 - but it looks like the docker image has not been released yet. The badge in the README.md indicates that the build might be failing!

Just thought we'd pass that along! ^_^
Thanks!

To check issue flow between github and linear