GithubHelp home page GithubHelp logo

ci-testing's People

Contributors

jnsgruk avatar snapcrafters-bot avatar

Watchers

 avatar

ci-testing's Issues

Call for testing `ci-testing`

A new version () of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd6428
arm6429

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 28,29 stable done

Call for testing `ci-testing`

A new version (0.2.3) of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd6476
arm6477

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 76,77 stable done

Call for testing `ci-testing`

A new version (0.2.3) of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd6436
arm6438

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 36,38 stable done

Call for testing `ci-testing`

A new version (0.2.3) of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd6466
arm6465

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 66,65 stable done

Call for testing `ci-testing`

A new version () of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd6420
arm6421

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 20,21 stable done

Call for testing `ci-testing`

A new version () of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd6426
arm6427

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 26,27 stable done

Call for testing `ci-testing`

A new version (0.2.3) of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd6480
arm6481

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 80,81 stable done

Call for testing `ci-testing`

A new version (0.2.3) of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd6436
arm6437

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 36,37 stable done

Call for testing `ci-testing`

A new version () of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd646
arm647

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 6,7 stable done

Call for testing `ci-testing`

A new version (0.2.3) of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd6487
arm6488

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 87,88 stable done

Call for testing `ci-testing`

A new version () of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd6414
arm6415

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 14,15 stable done

Call for testing `ci-testing`

A new version (0.2.3) of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd6459
arm6460

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 59,60 stable done

Call for testing `ci-testing`

A new version (0.2.3) of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd6478
arm6479

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 78,79 stable done

Call for testing `ci-testing`

A new version (0.2.3) of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd6455
arm6456

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 55,56 stable done

Call for testing `ci-testing`

A new version (0.2.3) of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd6485
arm6486

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 85,86 stable done

Call for testing `ci-testing`

A new version (0.2.3) of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd6458
arm6457

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 58,57 stable done

Call for testing `ci-testing`

A new version () of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd644
arm645

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 4,5 stable done

Call for testing `ci-testing`

A new version (0.2.3) of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd6489
arm6490

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 89,90 stable done

Call for testing `ci-testing`

A new version (0.2.3) of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd6461
arm6462

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 61,62 stable done

Call for testing ``

A new version (0.2.3) of was just pushed to the channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd641
arm64

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh  --
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info  | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 1, stable done

Call for testing `ci-testing`

A new version () of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd6424
arm6425

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 24,25 stable done

Call for testing `ci-testing`

A new version (0.2.3) of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd6453
arm6454

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 53,54 stable done

Call for testing `ci-testing`

A new version (0.2.3) of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd6468
arm6469

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 68,69 stable done

Call for testing `ci-testing`

A new version (0.2.3) of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd641
arm64

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 1, stable done

Call for testing `ci-testing`

A new version (0.2.3) of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd6470
arm6471

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 70,71 stable done

Call for testing `ci-testing`

A new version () of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd6413
arm6412

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 13,12 stable done

Call for testing `ci-testing`

A new version () of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd649
arm648

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 9,8 stable done

Call for testing `ci-testing`

A new version (0.2.2) of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd6431
arm6432

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 31,32 stable done

Call for testing `ci-testing`

A new version () of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd6410
arm6411

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 10,11 stable done

Call for testing `ci-testing`

A new version (0.2.3) of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd6474
arm6475

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 74,75 stable done

Call for testing `ci-testing`

A new version (0.2.3) of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd6434
arm6433

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 34,33 stable done

Call for testing `ci-testing`

A new version (0.2.3) of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd6463
arm6464

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 63,64 stable done

Call for testing `ci-testing`

A new version () of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd6422
arm6423

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 22,23 stable done

Call for testing `ci-testing`

A new version (0.2.3) of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd6482
arm6483

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 82,83 stable done

Call for testing `ci-testing`

A new version (0.2.3) of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd6472
arm6473

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 72,73 stable done

Call for testing `ci-testing`

A new version (0.2.3) of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd642
arm643

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 2,3 stable done

Call for testing `ci-testing`

A new version (0.2.3) of ci-testing was just pushed to the candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd6439
arm6440

Automated screenshots

The snap will be installed in a VM automatically; screenshots will be posted as a comment on this issue shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh ci-testing --candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info ci-testing | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] stable [done].

For example

  • To promote a single revision, run /promote <rev> stable
  • To promote multiple revisions, run /promote <rev>,<rev> stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> stable done

You can promote all revisions that were just built with:

/promote 39,40 stable done

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.